Method and apparatus for configuring QoS flow in wireless communication system

ABSTRACT

The present disclosure relates to a communication method and system for converging a 5th-Generation (5G) communication system for supporting higher data rates beyond a 4th-Generation (4G) system with a technology for Internet of Things (IoT). The present disclosure may be applied to intelligent services based on the 5G communication technology and the IoT-related technology, such as smart home, smart building, smart city, smart car, connected car, health care, digital education, smart retail, security and safety services. The present disclosure relates to a method and an apparatus for configuring a QoS flow in a mobile communication system.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a Continuation of U.S. Ser. No. 15/974,138, whichwas filed in the U.S. Patent and Trademark Office on May 8, 2018, andclaims priority under 35 U.S.C. § 119(a) to Korean Patent ApplicationSerial No. 10-2017-0057434, which was filed in the Korean IntellectualProperty Office on May 8, 2017, the entire disclosure of each of whichis incorporated herein by reference.

BACKGROUND 1. Field

The disclosure relates, generally, to an electronic device, and moreparticularly, to an electronic device that uses a method for configuringa quality of service (QoS) flow in a mobile communication system.

2. Description of the Related Art

To meet the demand for wireless data traffic having increased sincedeployment of 4G communication systems, efforts have been made todevelop an improved 5G or pre-5G communication system. Therefore, the 5Gor pre-5G communication system is also called a ‘Beyond 4G Network’ or a‘Post LTE System’.

The 5G communication system is considered to be implemented in higherfrequency (mmWave) bands, e.g., 60 GHz bands, so as to accomplish higherdata rates. To decrease propagation loss of the radio waves and increasethe transmission distance, the beamforming, massive multiple-inputmultiple-output (MIMO), Full Dimensional MIMO (FD-MIMO), array antenna,an analog beam forming, large scale antenna techniques are discussed in5G communication systems.

In addition, in 5G communication systems, development for system networkimprovement is under way based on advanced small cells, cloud RadioAccess Networks (RANs), ultra-dense networks, device-to-device (D2D)communication, wireless backhaul, moving network, cooperativecommunication, Coordinated Multi-Points (CoMP), reception-endinterference cancellation and the like. In the 5G system, Hybrid FSK andQAM Modulation (FQAM) and sliding window superposition coding (SWSC) asan advanced coding modulation (ACM), and filter bank multi carrier(FBMC), non-orthogonal multiple access (NOMA), and sparse code multipleaccess (SCMA) as an advanced access technology have been developed.

The Internet, which is a human centered connectivity network wherehumans generate and consume information, is now evolving to the Internetof Things (IoT) where distributed entities, such as things, exchange andprocess information without human intervention. The Internet ofEverything (IoE), which is a combination of the IoT technology and theBig Data processing technology through connection with a cloud server,has emerged. As technology elements, such as “sensing technology”,“wired/wireless communication and network infrastructure”, “serviceinterface technology”, and “Security technology” have been demanded forIoT implementation, a sensor network, a Machine-to-Machine (M2M)communication, Machine Type Communication (MTC), and so forth have beenrecently researched. Such an IoT environment may provide intelligentInternet technology services that create a new value to human life bycollecting and analyzing data generated among connected things. IoT maybe applied to a variety of fields including smart home, smart building,smart city, smart car or connected cars, smart grid, health care, smartappliances and advanced medical services through convergence andcombination between existing Information Technology (IT) and variousindustrial applications.

In line with this, various attempts have been made to apply 5Gcommunication systems to IoT networks. For example, technologies such asa sensor network, Machine Type Communication (MTC), andMachine-to-Machine (M2M) communication may be implemented bybeamforming, MIMO, and array antennas. Application of a cloud RadioAccess Network (RAN) as the above-described Big Data processingtechnology may also be considered to be as an example of convergencebetween the 5G technology and the IoT technology.

On the other hand, in order to satisfy various QoS requirements of OTT,a 5G system uses reflective QoS, flexible QoS, and non-standardized QoSclass, which are new features. Further, for QoS differentiation in abackhaul portion, the 5G system uses transport level marking that hasalso been used in LTE.

SUMMARY

The present disclosure has been made to address at least thedisadvantages described above and to provide at least the advantagesdescribed below.

In accordance with an aspect of the disclosure, there is provided amethod performed by a base station in a wireless communication system.The method includes receiving, from a session management function (SMF)entity, information on transport level packet marking for uplink data ofa terminal; receiving, from the terminal, the uplink data; performingthe transport level packet marking in an internet protocol (IP) headerfor the uplink data based on the information; and transmitting, to auser plane function (UPF) entity, the uplink data with the IP header.

In accordance with an aspect of the disclosure, there is provided amethod performed by a user plane function (UPF) entity in a wirelesscommunication system. The method includes receiving, from a sessionmanagement function (SMF) entity, information on transport level packetmarking for downlink data for a terminal; performing the transport levelpacket marking in an internet protocol (IP) header for the downlink databased on the information; and transmitting, to a base station, thedownlink data with the IP header.

In accordance with an aspect of the disclosure, there is provided a basestation in a wireless communication system. The base station includes atransceiver; and a controller coupled with the transceiver andconfigured to receive, from a session management function (SMF) entity,information on transport level packet marking for uplink data of aterminal, receive, from the terminal, the uplink data, perform thetransport level packet marking in an internet protocol (IP) header forthe uplink data based on the information, and transmit, to a user planefunction (UPF) entity, the uplink data with the IP header.

In accordance with an aspect of the disclosure, there is provided a userplane function (UPF) entity in a wireless communication system. The UPFentity includes a transceiver; and a controller coupled with thetransceiver and configured to receive, from a session managementfunction (SMF) entity, information on transport level packet marking fordownlink data for a terminal, perform the transport level packet markingin an internet protocol (IP) header for the downlink data based on theinformation, and transmit, to a base station, the downlink data with theIP Header.

In accordance with an aspect of the disclosure, there is provided amethod performed by a terminal in a wireless communication system. Themethod includes generating uplink data of the terminal; andtransmitting, to a base station, the uplink data. Information ontransport level packet marking for the uplink data is received by thebase station from a session management function (SMF) entity. Thetransport level packet marking is performed by the base station in aninternet protocol (IP) header for the uplink data based on theinformation. The uplink data with the IP header is transmitted by thebase station to a user plane function (UPF) entity.

In accordance with an aspect of the disclosure, there is provided aterminal in a wireless communication system. The terminal includes atransceiver; and a controller coupled with the transceiver andconfigured to generate uplink data of the terminal, and transmit, to abase station, the uplink data. Information on transport level packetmarking for the uplink data is received by the base station from asession management function (SMF) entity. The transport level packetmarking is performed by the base station in an internet protocol (IP)header for the uplink data based on the information. The uplink datawith the IP header is transmitted by the base station to a user planefunction (UPF) entity.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features and advantages of certainembodiments of the disclosure will be more apparent from the followingdetailed description taken in conjunction with the accompanyingdrawings, in which:

FIG. 1 is a diagram of a 5G system, according to an embodiment;

FIG. 2 is a diagram of reflective QoS, according to an embodiment;

FIG. 3 is a flowchart of a method of for a protocol data unit (PDU)session establishment procedure, according to an embodiment;

FIG. 4 is a flowchart of a PDU session modification procedure, accordingto an embodiment;

FIG. 5 is a diagram of a QoS rule that applies for a session managementfunction (SMF) that transfers to a user equipment (UE), according to anembodiment;

FIG. 6 is a diagram explaining a QoS profile that applies for an SMFthat transfers to a RAN, according to an embodiment;

FIG. 7 is a diagram explaining a QoS rule that an SMF transfers to auser plane function (UPF), according to an embodiment;

FIG. 8 is a flowchart of a method for transferring a data packet indownlink/uplink (DL/UL), according to an embodiment;

FIG. 9 is a flowchart of a DL packet processing method, according towhether a UE supports reflective QoS (RQ) of a QoS flow and an RQ type,according to an embodiment;

FIG. 10 is a diagram of a terminal, according to an embodiment;

FIG. 11 is a diagram of a base station, according to an embodiment; and

FIG. 12 is a diagram of a network entity, according to an embodiment.

DETAILED DESCRIPTION

Embodiments of the disclosure will be described herein below withreference to the accompanying drawings. However, the embodiments of thedisclosure are not limited to the specific embodiments and should beconstrued as including all modifications, changes, equivalent devicesand methods, and/or alternative embodiments of the present disclosure.In the description of the drawings, similar reference numerals are usedfor similar elements.

The terms “have,” “may have,” “include,” and “may include” as usedherein indicate the presence of corresponding features (for example,elements such as numerical values, functions, operations, or parts), anddo not preclude the presence of additional features.

The terms “A or B,” “at least one of A or/and B,” or “one or more of Aor/and B” as used herein include all possible combinations of itemsenumerated with them. For example, “A or B,” “at least one of A and B,”or “at least one of A or B” means (1) including at least one A, (2)including at least one B, or (3) including both at least one A and atleast one B.

The terms such as “first” and “second” as used herein may usecorresponding components regardless of importance or an order and areused to distinguish a component from another without limiting thecomponents. These terms may be used for the purpose of distinguishingone element from another element. For example, a first user device and asecond user device may indicate different user devices regardless of theorder or importance. For example, a first element may be referred to asa second element without departing from the scope the disclosure, andsimilarly, a second element may be referred to as a first element.

It will be understood that, when an element (for example, a firstelement) is “(operatively or communicatively) coupled with/to” or“connected to” another element (for example, a second element), theelement may be directly coupled with/to another element, and there maybe an intervening element (for example, a third element) between theelement and another element. To the contrary, it will be understoodthat, when an element (for example, a first element) is “directlycoupled with/to” or “directly connected to” another element (forexample, a second element), there is no intervening element (forexample, a third element) between the element and another element.

The expression “configured to (or set to)” as used herein may be usedinterchangeably with “suitable for,” “having the capacity to,” “designedto,” “adapted to,” “made to,” or “capable of” according to a context.The term “configured to (set to)” does not necessarily mean“specifically designed to” in a hardware level. Instead, the expression“apparatus configured to . . . ” may mean that the apparatus is “capableof . . . ” along with other devices or parts in a certain context. Forexample, “a processor configured to (set to) perform A, B, and C” maymean a dedicated processor (e.g., an embedded processor) for performinga corresponding operation, or a generic-purpose processor (e.g., acentral processing unit (CPU) or an application processor (AP)) capableof performing a corresponding operation by executing one or moresoftware programs stored in a memory device.

The terms used in describing the various embodiments of the disclosureare for the purpose of describing particular embodiments and are notintended to limit the disclosure. As used herein, the singular forms areintended to include the plural forms as well, unless the context clearlyindicates otherwise. All of the terms used herein including technical orscientific terms have the same meanings as those generally understood byan ordinary skilled person in the related art unless they are definedotherwise. The terms defined in a generally used dictionary should beinterpreted as having the same or similar meanings as the contextualmeanings of the relevant technology and should not be interpreted ashaving ideal or exaggerated meanings unless they are clearly definedherein. According to circumstances, even the terms defined in thisdisclosure should not be interpreted as excluding the embodiments of thedisclosure.

The term “module” as used herein may, for example, mean a unit includingone of hardware, software, and firmware or a combination of two or moreof them. The term “module” may be interchangeably used with, forexample, the term “unit”, “logic”, “logical block”, “component”, or“circuit”. The “module” may be a minimum unit of an integrated componentelement or a part thereof. The “module” may be a minimum unit forperforming one or more functions or a part thereof. The “module” may bemechanically or electronically implemented. For example, the “module”according to the disclosure may include at least one of anapplication-specific integrated circuit (ASIC) chip, afield-programmable gate array (FPGA), and a programmable-logic devicefor performing operations which has been known or are to be developedhereinafter.

An electronic device according to the disclosure may include at leastone of, for example, a smart phone, a tablet personal computer (PC), amobile phone, a video phone, an electronic book reader (e-book reader),a desktop PC, a laptop PC, a netbook computer, a workstation, a server,a personal digital assistant (PDA), a portable multimedia player (PMP),a MPEG-1 audio layer-3 (MP3) player, a mobile medical device, a camera,and a wearable device. The wearable device may include at least one ofan accessory type (e.g., a watch, a ring, a bracelet, an anklet, anecklace, a glasses, a contact lens, or a head-mounted device (HMD)), afabric or clothing integrated type (e.g., an electronic clothing), abody-mounted type (e.g., a skin pad, or tattoo), and a bio-implantabletype (e.g., an implantable circuit).

The electronic device may be a home appliance. The home appliance mayinclude at least one of, for example, a television, a digital video disk(DVD) player, an audio, a refrigerator, an air conditioner, a vacuumcleaner, an oven, a microwave oven, a washing machine, an air cleaner, aset-top box, a home automation control panel, a security control panel,a TV box (e.g., Samsung HomeSync™, Apple TV™, or Google TV™), a gameconsole (e.g., Xbox™ and PlayStation™), an electronic dictionary, anelectronic key, a camcorder, and an electronic photo frame.

The electronic device may include at least one of various medicaldevices (e.g., various portable medical measuring devices (a bloodglucose monitoring device, a heart rate monitoring device, a bloodpressure measuring device, a body temperature measuring device, etc.), amagnetic resonance angiography (MRA), a magnetic resonance imaging(MRI), a computed tomography (CT) machine, and an ultrasonic machine), anavigation device, a global positioning system (GPS) receiver, an eventdata recorder (EDR), a flight data recorder (FDR), a vehicleinfotainment device, an electronic device for a ship (e.g., a navigationdevice for a ship, and a gyro-compass), avionics, security devices, anautomotive head unit, a robot for home or industry, an automatic tellermachine (ATM) in banks, point of sales (POS) devices in a shop, or anIoT device (e.g., a light bulb, various sensors, electric or gas meter,a sprinkler device, a fire alarm, a thermostat, a streetlamp, a toaster,a sporting goods, a hot water tank, a heater, a boiler, etc.).

The electronic device may include at least one of a part of furniture ora building/structure, an electronic board, an electronic signaturereceiving device, a projector, and various kinds of measuringinstruments (e.g., a water meter, an electric meter, a gas meter, and aradio wave meter). The electronic device may be a combination of one ormore of the aforementioned various devices. The electronic device mayalso be a flexible device. Further, the electronic device is not limitedto the aforementioned devices, and may include an electronic deviceaccording to the development of new technology.

Hereinafter, an electronic device will be described with reference tothe accompanying drawings. In the disclosure, the term “user” mayindicate a person using an electronic device or a device (e.g., anartificial intelligence electronic device) using an electronic device.

In accordance with the disclosure, a method and an apparatus forconfiguring a QoS flow is now herein described in detail with referenceto the accompanying drawings.

FIG. 1 is a diagram of a 5G system, according to an embodiment.

Referring to FIG. 1, a 5G system may include a terminal (user equipment(UE)) 110, a RAN 115, a UPF 120, a data network (DN) 125, a user datamanagement (UDM) 130, an access & mobility function (AMF) 135, a sessionmanagement function (SMF) 140, a policy control function (PCF) 145, anapplication function (AF) 150, and an authentication server function(AUSF) 155.

The 5G system uses reflective QoS, flexible QoS, and non-standardizedQoS class in order to satisfy various QoS requirements of OTT. Further,the 5G system uses transport level marking that has also been used inLTE for QoS differentiation in a backhaul portion.

FIG. 2 is a diagram of reflective QoS, according to an embodiment.

1) RQ

The RQ is a scheme for the UE to generate a UL QoS rule based on areceived downlink data packet. In one PDU session, both a QoS flow usingthe RQ and a QoS flow that does not use the RQ may exist.

There are two kinds of RQ activation schemes.

Reflective QoS Activation Via User Plane

If the UPF120 receives a packet of an internet protocol (IP) flowcorresponding to a QoS rule intended to be changed from an external DN,the UPF 120 configures a reflective QoS indication (RQI) field to 1 inan encapsulation header of the received DL packet, and transfers the DLpacket with the configured RQI field to an N3 interface. The UE 110having received the DL packet with the configured RQI field makes theQoS rule for UL using an IP and a transmission control protocol (TCP) ofthe received DL packet or UDP header information.

Reflective QoS Activation Via Control Plane

If the UE 110 receives the QoS rule including the RQI from the SMF 140and receives the DL packet matching the QoS rule, the UE 110 generatesthe UL QoS rule from the received DL packet.

2) Flexible QoS

As compared with the LTE in which the relationship between an evolvedpacket system (EPS) bearer that is a QoS unit and a data radio bearer(DRB) is 1:1, in the 5G system, the relationship between the QoS flowand the DRB can be n:1 (n≥1). For example, if a plurality of QoS flowssatisfy the QoS requirements, a 5G base station (RAN 115) can transferthe packet to the UE 110 using one DRB. The RAN 115 determines andconnects the DRB relationship of the QoS flows, but a 5G system centernetwork (5G core network (5GC)) is unable to know the connectionrelationship.

3) Non-Standardized QoS Class

As compared with the LTE in which only a determined QoS class issupported, in the 5G system, the QoS class can be defined without limit.For this, two kinds of 5G QoS indicators (5Qis) are used in the 5Gsystem.

Standardized 5QI

The QoS characteristics called by the standardized 5QI, that is,resource type, priority level, packet delay budget (PDB), and packeterror rate (PER), are preconfigured in devices of the 5G system. The PF120, UE 110, and RAN 115, and thus the QoS characteristics can be knownonly by the 5QI without separate signaling.

Non-Standardized 5QI

As needed, the QoS characteristics called by the non-standardized 5QIare dynamically determined by the 5GC, and the determined QoScharacteristics, together with the 5QI, are transferred to the devicesof the 5G system.

If the non-standardized 5QI is used, the QoS class can be freely definedin addition to the predetermined QoS class in the 5G system.

4) Transport Level Packet Marking

In the LTE, transport level marking is used for QoS differentiation in abackhaul network (network for data transmission between a primarygateway (P-GW) and an evolved-node B (eNB). The transport level markingis a gateway (GW) and an eNB in the LTE perform QoS differentiationmarking in L3 or L2 layer header of the backhaul network based on QoSclass index (QCI) and ARP of the LTE. For example, the GW or eNB marks asuitable value in a differentiated services code point (hereinafter,DSCP) field of an outer IP header in consideration of the QCI andaddress resolution protocol (ARP) of the EPS bearer. Even in the 5Gsystem, the RAN 115 and the UPF 120 perform transport level packetmarking to provide the QoS in the backhaul network.

However, in accordance with the use of the reflective QoS, thecomputation load of the DL packet of the UE 110 may be increased. Thedetection load of per packet inspection and new IP flow may beincreased, and the computation load of the packet of the terminal to becomputed per hour in accordance with the 5G speed improvement may beincreased. With regard to each header for transferring QoS informationto the UE 110, a new header is used in a radio section to transfer QoSflow ID (QFI) and reflective QoS indication (RQI), and when the transferof the QFI and the RQI is not necessary, the waste of the radioresources occurs (e.g., IoT device). There may be a need for schemes toprovide a QoS in a backhaul portion in the 5G system. In order to easethe support of the new QoS class in the 5G, non-standardized 5QI becomespossible, and it may be difficult to preconfigure the 5QI and the DSCPmapping.

In order to solve the problem of the computation load of a DL packet ofa terminal that is increased due to the use of the reflective QoS, thedisclosure can provide transfer of an RQ support/nonsupport of the UE110 and an RQ type, determination of an RQ support/nonsupport of a CNfor each QoS flow and a support type in consideration of the RQsupport/nonsupport of the UE and QoS requirements, transfer the RQsupport/nonsupport of the core network (CN) for each QoS flow to the UE110 and an RQ type, and DL packet computation differentiation inaccordance with the RQ support/nonsupport of the QoS flow of the UE 110and the support type.

In order to solve the problem of the occurrence of the waste of theradio resources, the disclosure can transfer an RQ support/nonsupport ofthe core network (CN) for each QoS flow to the RAN 115, QoS flow to DRBmapping in accordance with the RQ support/nonsupport of the QoS flow ofthe RAN 115 and the RQ type, and

RQ support header configuration of the DRB in accordance with the RQsupport/nonsupport of the QoS flow of the RAN 115 and the RQ type.

Further, in a backhaul portion to be provided in the 5G system, thedisclosure can provide determination of the transport level markingvalue during generation of the QoS flow in consideration of the QoSrequirements of the CN and the N3 path situation between the UPF 120 andthe RAN 115 and transfer the transport level marking value for each QoSflow to the CN UPF 120 and RAN 115.

First Embodiment—PDU Session Establishment Procedure

FIG. 3 is a flowchart of a method of for a PDU session establishmentprocedure, according to an embodiment.

1. [UE→AMF] Session establishment is requested by transferring a sessionestablishment request. The session establishment request includes RQtypes that can be supported by the UE (302). The RQ types may include RQnonsupport, RQ via control plane (RQ via C or RQvC) support only (RQvConly), RQ via user plane (RQ via U or RQvU) support only (RQvU only),and both RQ via C and RQ via U supportable (RQvCvU).

2. (AMF) An AMF selects an SMF (304).

3. [AMF→SMF] A PDU session establish request is transferred to the SMFselected in procedure 2 (306).

4. [SMF→WDM] The SMF requests and receives UE subscription informationfrom a UDM (308).

5. PDU session authentication procedure (310).

6. (SMF) The SMF can select a PCF. In this case, the SMF can receive aQoS policy to be used by the UE from the PCF (312 and 314).

7. (SMF) The SMF selects a UPF to be used by a session between the UEand a DN (316).

8. (SMF→PCF) The SMF can receive a QoS policy rule to be used by the UEfrom the PCF (318). The SMF determines items of [Third Embodiment] and[Fourth Embodiment] in consideration of RQ support/nonsupport of the UEin procedure 1 and an RQ type and the QoS policy of the PCF in procedure6.

UL and DL transport level packet marking of [Fourth Embodiment] and[Fifth Embodiment] is determined in consideration of the QoS policy ofthe PCF in procedure 6 and a backhaul state between the UPF and a RAN.

9. (SMF→UPF) If the session establishment has been performed inprocedure 5, the SMF sends an N4 session modification request to theUPF. The N4 session modification request includes [Fifth Embodiment]determined in procedure 8 (320).

10. (SMF→AMF) The SMF transfers an SM response to the AMF. The SMresponse may include the followings: Cause, N2 SM information, and N1 SMinformation. The N2 SM information includes a PDU session ID, QoSProfile(s), and CN Tunnel Info. The N1 SM information includes a PDUsession establishment accept (authorized QoS rule, SSC(Session andService Continuity) mode, S-NSSAI (single network slice selectionassistance information), and allocated IPv4 address) (322).

The QoS Profile includes [Fourth Embodiment] of QoS flows to be used fora RAN session.

The authorized QoS rule includes [Third Embodiment] of QoS flows to beused for a UE session.

11. (AMF→RAN) The AMF transfers an N2 PDU session request to the RAN.The AMF transfers to the RAN a NAS message including the PDU session IDand the PDU session establishment accept (324).

12. (RAN→UE) The RAN configures a DRB as in [Sixth Embodiment] (326).

The RAN transfers to the UE the NAS message (PDU session ID, N1 SMinformation (PDU session establishment accept)) received in procedure11.

13. (RAN→AMF) Response to a request in procedure 11 (328).

14. (AMF→SMF) The SM request (N2 SM information) is transferred (332).

15. (SMF→UPF) If the PDU session has not been made, the SMF transfers anN4 session establishment message to the UPF to request the UPF togenerate the PDU session, whereas if the PDU session has been made, theSMF transfers an N4 session modification to request the UPF to changethe PDU session (334).

The N4 session establishment and the N4 session modification include[Fifth Embodiment].

16. (SMF→AMF) Response in procedure 14 (336).

17. (SMF→UE) IPv6 configuration information can be transferred (338).

18. If the PDU session establishment is a handover from non-3GPP accessto 3GPP access, the session in the non-3GPP access is released (342).

19. The UDM stores SMF id, SMF address, and DNN (344).

Second Embodiment—PDU Session Modification Procedure

FIG. 4 is a flowchart of a PDU session modification procedure, accordingto an embodiment.

1. Start of the procedure may be as follows.

A. UE initiates the PDU session modification procedure throughtransmission of a PDU session modification over N1 (402).

B. A PCF initiates a PDU-CAN session modification procedure upon policydecision triggered by DPI's traffic detection notification or upon AFrequests (404 and 406).

C. A UDM sends an insert subscriber data message to an SMF (408).

D. The SMF may decide to modify a PDU session. This procedure may alsobe triggered based on a locally configured policy (410).

E. A (R)AN sends an N2 message (PDU session ID and SM information) to anAMF. The SM information includes a QFI and a notification indicatingthat QoS targets cannot be fulfilled. The AMF sends an SM request (SMinformation) message to the SMF (412 and 414).

2. (SMF→PCF) The SMF requests a changed QoS policy from the PCF, and thePCF transfers the changed QoS policy to the SMF. The SMF determinesitems of [Third Embodiment] and [Fourth Embodiment] in consideration ofRQ support/nonsupport of the UE in procedure 1 of [First Embodiment] andan RQ type and the QoS policy of the PCF (416).

UL and DL transport level packet marking of [Fourth Embodiment] and[Fifth Embodiment] is determined in consideration of the QoS policy ofthe PCF and a backhaul state between the UPF and a RAN.

3. (SMF→AMF) The SMF transfers to the AMF an SM request message (N2 SMinformation (PDU session ID, QoS profile, and session-AMBR), N1 SMcontainer (PDU session modification command (PDU session ID, QoS rule,and session-AMBR))) (418).

The N2 SM information includes a PDU Session ID, QoS Profile(s), and asession AMBR.

The N1 SM information includes a PDU session modification command (PDUsession id, QoS Rule, and session AMBR).

The QoS profile includes [Fourth Embodiment] of QoS flows to be used fora RAN session.

The authorized QoS rule includes [Third Embodiment] QoS flows to be usedfor a UE session.

4. (AMF→RAN) The AMF transfers an N2 PDU session request message to theRAN (420).

The N2 PDU session request includes N2 SM information in procedure 3.

A NAS message includes a PDU session modification command in procedure3.

5. (RAN→UE) DRB configuration change of the RAN (422).

The NAS message in procedure 4 is transferred to the UE.

DRB configuration may be changed in accordance with the N2 SMinformation transferred in procedure 3. In this case, the DRBconfiguration can be performed as in [Sixth Embodiment].

6. (RAN→AMF) Response in procedure 4 (424).

7. (AMF→SMF) Response in procedure 3 (426).

8. (SMF→UPF) The SMF may request a PDU session change by transferring anN4 session modification to the UPF (428).

The N4 session modification includes [Fifth Embodiment].

9. (SMF→PCF) The SMF may notify the PCF that the QoS policy has beenconfigured (430).

Third Embodiment—QoS Rule that the SMF Transfers to the UE

The SMF transfers to the UE a QoS rule to be used during UL trafficdiscrimination and QoS security. FIG. 5 is a diagram of a QoS rule thatapplies for an SMF that transfers to a UE, according to an embodiment.The QoS rule transferred to the UE may include the following contents.

-   -   QoS rule ID (502): Identification number for discriminating the        QoS rule configured in the UE during control of the QoS Rule.    -   QoS flow ID (QFI) (504): Identification number marked on a DL        packet to be transferred to the UE in order to discriminate the        QoS flow indicated by this QoS rule, or marked by the UE on a UL        packet for the QoS process of a UL traffic. When using the        standard designation 5QI, the QFI may have the same value as the        value of the 5QI.    -   QoS flow template (506): A set of packet filters for applying        the UL traffic during selection of the QoS flow corresponding to        the QoS rule; this may be omitted if a default QoS rule or        reflective QoS is supported.    -   Precedence value (508): The order of applying this QoS rule to        the UL traffic.    -   5G QoS characteristic indication (5QI) (510): An identifier        indicating the QoS processing characteristic received when the        QoS flow indicated by the QoS rule is processed in the 5G        system. The 5QI may have a value designated in the standard or a        value optionally selected by the SMF. With respect to the        standard designated value, the 5QI may be omitted.    -   QoS parameters (512): Parameters required for the QoS processing        characteristic of the QoS flow indicated by this QoS rule. The        parameters may be a flow type, priority level, packet delay        budge, packet error rate, guaranteed flow bit rate, maximum flow        bit rate, and notification control. One or more of the QoS        parameters may be omitted if they already known to the UE.    -   Reflective QoS support (514): Reflective QoS type supported by        the QoS flow indicated by this QoS Rule. The Reflective QoS type        may be nonsupport/reflective QoS via control plane and/or        reflective QoS via user plane.

Fourth Embodiment—QoS Profile that the SMF Transfers to the RAN

The SMF transfers to the RAN a QoS profile indicating the QoScharacteristic to be used during QoS security of DL and UL traffic.

FIG. 6 is a diagram explaining a QoS profile that applies for an SMFthat transfers to a RAN, according to an embodiment. The QoS profiletransferred to the RAN may include the following contents.

-   -   QoS rule ID (602): Identification number for discriminating the        QoS rule configured in the UE during control of the QoS Rule.    -   QoS flow ID (QFI) (604): Identification number marked on a DL        packet to be transferred to the UE in order to discriminate the        QoS flow indicated by this QoS rule, or marked by the UE on a UL        packet for the QoS process of a UL traffic.    -   5G QoS characteristic indication (5QI) (606): An identifier        indicating the QoS processing characteristic received when the        QoS flow indicated by this QoS rule is processed in the 5G        system. The 5QI may have a value designated in the standard or a        value optionally selected by the SMF. With respect to the        standard designated value, the 5QI may be omitted.    -   QoS parameters (608): Parameters required for the QoS processing        characteristic of the QoS flow indicated by this QoS rule. The        parameters may be a flow type, priority level, packet delay        budge, packet error rate, guaranteed flow bit rate, maximum flow        bit rate, and notification control. One or more of the QoS        parameters may be omitted when they are already known to the UE        (e.g., during the use of the standard designation 5QI).    -   Reflective QoS support (610): Reflective QoS type supported by        the QoS flow indicated by this QoS Rule. It may be one of        nonsupport/reflective QoS via control plane and reflective QoS        via user plane.    -   Transport level packet marking (612): Transport level packet        marking in the uplink, e.g., DiffSery code point (DSCP), to be        applied for the traffic identified for this QoS Flow, which can        be DSCP value and/or MPLS (Multiprotocol Label Switching) TOS        (Type of Service) value. The transport level packet marking may        be determined in consideration of the QoS characteristic, ARP,        and backhaul state between the UPF and the RAN (expected        congestion level and expected round trip time (RTT) between the        UPF and the RAN).

Fifth Embodiment—QoS Rule that the SMF Transfers to the UPF

The SMF transfers to the UPF a QoS rule to be used during DL trafficdiscrimination and QoS security. FIG. 7 is a diagram explaining a QoSrule that an SMF transfers to a user plane function (UPF) according toan embodiment of the present disclosure. The QoS rule transferred to theUPF may include the following contents.

-   -   QoS rule ID (702): Identification number for discriminating the        QoS rule configured in the UE during control of the QoS Rule.    -   QoS flow ID (QFI) (704): Identification number marked by the UPF        on a DL packet in order to discriminate the QoS flow indicated        by this QoS rule. When using the standard designation 5QI, the        QFI may have the same value as the value of the 5QI.    -   QoS flow template (706): A set of packet filters applying the DL        traffic during selection of the QoS flow corresponding to the        QoS rule. When the QoS rule is defaulted, it may be omitted.    -   Precedence value (708): The order of applying this QoS rule to        the DL traffic.    -   5G QoS characteristic indication (5QI, 710): An identifier        indicating the QoS processing characteristic received when the        QoS flow indicated by this QoS rule is processed in the 5G        system. The 5QI may have a value designated in the standard or a        value optionally selected by the SMF. With respect to the        standard designated value, the 5QI may be omitted.    -   QoS parameters (712): Additional QoS parameter information for        DRB configuration matching the QoS flow. Detailed items thereof        may be a flow type (GBR (guaranteed bitrate)/non-GBR), priority,        packet delay budget, packet error rate, guaranteed flow bit rate        (e.g., GBR QoS flow), and maximum flow bit rate.    -   Transport level packet marking (714): Transport level packet        marking in the downlink, e.g., DiffSery code point (DSCP), to be        applied for the traffic identified for this QoS Flow, which can        be the DSCP value and/or the MPLS TOS value. The transport level        packet marking may be determined in consideration of the QoS        characteristic, ARP, and backhaul state between the UPF and the        RAN (expected congestion level and expected RTT between the UPF        and the RAN).

Sixth Embodiment—Data Radio Bearer Configuration Operation in Accordancewith RQ Support/Nonsupport and RQ Type of QoS Flow of RAN

The RAN having received one or a plurality of QoS profiles] from one ora plurality of QoS flows transferred by a PDU session determines thenumber of data radio bearers (DRBs) to be used to transfer the QoS flowsbetween the UE and the RAN and configuration of the data radio bearer(DBR).

If it is determined that it is not necessary for one or a plurality ofthe DL QoS flows to be transferred through a certain DRB to transfer theDL QFI and RQI with reference to the QoS profile, the RAN may determinenot to use a Uu header for transfer of the QFI and the RQI during DRBconfiguration. In this case, such DRB configuration should be notifiedthe UE.

Cases where it is determined not to use the Uu header for the transferof the QFI and the RQI may be as follows.

1) When one QoS flow is transferred through a DRB, and this QoS flowdoes not support an RQ (i.e., RQ support element in QoSprofile=nonsupport).

2) When one QoS flow is transferred through a DRB, and this QoS flowsupports an RQ the type of which is RQvC (i.e., RQ support element inQoS profile=RQvC).

3) When a plurality of QoS flows transferred through a DRB do notsupport an RQ in all.

Seventh Embodiment—Data Packet Transfer Procedure

FIG. 8 is a flowchart of a method for transferring a data packet inDL/UL, according to an embodiment.

1. A UPF receives a DL data packet from a DN (802).

2. The UPF applies a QoS rule of [Fifth Embodiment] to the downlink datapacket received from the DN. That is, the UPF discovers (i.e., maps) aQoS flow to be applied based on IP flow information of the received datapacket. The UPF marks a mapped QoS flow id on an N3 header of the datapacket. The UPF may mark the mapped RQI on the N3 header of the datapacket. The UPF performs transport level packet marking (i.e., DSCPmarking or MPLS marking) included in the QoS rule (804).

3. The UPF transfers the data packet to a RAN. In this case, QFI and RQIare marked on the N3 header of the data packet, and the transport levelpacket marking is made in an outer header (i.e., outer IP or L2 header)(806).

4. The RAN having received this applies the DRB configured through[Sixth Embodiment] in accordance with the QFI of the DL packet. That is,in accordance with the DRB application, the RAN may use or omit a Uuheader for the QFI and RQI (808).

5. The UE receives the DL data packet, and performs an operation of[Eighth Embodiment] based on the received DL data packet. That is, inaccordance with RQ support/nonsupport of the QoS flow and an RQ type,the UE updates UE UL QoS rule (i.e. uplink traffic flow template (ULTFT)) (adds/removes a packet filter to/from the UP TFT) (810).

6. If a UL traffic occurs, the UE performs IP flow to QoS flow mappingby applying the UL QoS rule updated in the procedure 5, and marks theQoS flow id on the Uu header or omits the marking in accordance with theUL DRB configuration. The UE transfers the UL data packet to the RANthrough the Uu (812).

7. The RAN performs QFI marking and transport level packet marking onthe UL N3 header in accordance with the QoS profile of [FourthEmbodiment] of the received UL packet (814).

8. The RAN transfers the UL packet to the UPF through N3 (816).

9. The UPF transfers the received UL packet to the DN (818).

Eighth Embodiment—DL Packet Processing Operation in Accordance with RQSupport/Nonsupport and RQ Type of QoS Flow of UE

FIG. 9 is a flowchart of a DL packet processing method according towhether a UE supports RQ of a QoS flow and an RQ type, according to anembodiment.

0. If a DL packet is received, the UE starts a DL packet processingoperation.

1. The UE finds a QoS flow to which the DL packet belongs in accordancewith what DRB or QFI of the Uu header of the received DL packet the DLpacket is transferred through (910).

2. The UE identifies whether the QoS flow to which the DL packetidentified in 1 is a QoS flow supporting the RQ with reference to a ULQoS rule of [Third Embodiment] (915).

3. In case of the RQ support/nonsupport QoS flow, it is identifiedwhether the RQ type is RQvC or RQvU (920).

4. In case of the RQvU (if the RQ type is not RQvC), it is identifiedwhether an RQI field is configured in the Uu header of the DL packet(925).

5. In case of the RQvC, it is identified whether an IP flow indicated bya data header (inner IP header and inner TCP or UDP header) is a new IPflow in the UL TFT of the QoS rule to which the QoS flow belongs (935).

6. If the RQ type is RQvU and the RQI is not configured, it isidentified whether the IP flow indicated by the data header of the DLpacket is the new IP flow in the UL TFT of the QoS rule to which the QoSflow belongs (930).

7. If the RQ type is RQvU and the RQI is configured, it is identifiedwhether the IP flow indicated by the data header of the DL packet is thenew IP flow in the UL TFT of the QoS rule to which the QoS flow belongs(940).

8. If the RQ type is RQvU, the RQI is not configured, and the IP flow isdetermined as the new IP flow in procedure 6, a packet filter of the IPflow called by the received DL packet is deleted from the packet filterof the QoS rule made through the existing RQ (945).

9. If the RQ type is RQvU, the RQI is not configured, and the IP flow isdetermined as the new IP flow in procedure 7, a packet filter of the IPflow called by the received DL packet and a UL QoS rule having thereceived QoS flow id are made (950).

10. If the RQ type is RQvC, and the IP flow is determined as the new IPflow in procedure 5, a packet filter of the IP flow called by thereceived DL packet and a UL QoS rule having the received QoS flow id aremade (955).

11. The processed DL packet is transferred to an upper layer of the UE(960).

12. The procedure is ended.

The packet computation load of the UE is reduced, and the DL packetprocessing of the UE is performed relatively fast. Further, the use ofthe radio resources for the QoS support is saved, and the QoS reflectingvarious QoS requirements and backhaul network situations are secured inthe 5G backhaul network.

FIG. 10 is a diagram of a terminal, according to an embodiment.

A terminal 1000 may be one of the aforementioned electronic devices andmay include a transceiver 1020 and a controller 1010 configured tocontrol the overall operation of the terminal 100. The transceiver 1020may include a transmitter 1023 and a receiver 1025. The terminal mayfurther include a storage (e.g., memory) in addition to the transceiver1020 and the controller 1010.

The transceiver 1020 may transmit/receive signals with other networkentities.

The controller 1010 may control signal flow between respective blocks toperform the above-described methods of FIGS. 3, 4, 8 and 9. Thecontroller 1010 and the transceiver 1020 may be implemented by separatemodules, or they may be implemented by one constituent unit in the formof a single chip, a system on chip, etc.

The controller 1010 and the transceiver 1020 may be electricallyconnected to each other. For example, the controller 1010 may be orinclude a circuit, an application-specific circuit, or at least oneprocessor. Further, operations of the terminal 1000 may be implementedby providing a memory device storing corresponding program codes thereinon a certain constituent unit in the terminal 1000. The terminal 1000may also include any one of the aforementioned modules.

FIG. 11 is a diagram of a base station, according to an embodiment.

A base station 1100 may be one of the aforementioned electronic devicesand may include a transceiver 1120 and a controller 1110 configured tocontrol the overall operation of the base station 1100. The transceiver1120 may include a transmitter 1123 and a receiver 1125. The basestation 1100 may further include a storage in addition to thetransceiver 1120 and the controller 1110.

The transceiver 1120 may transmit/receive signals with other networkentities.

The controller 1110 may control the base station 1100 to perform any oneof the methods described with respect to FIGS. 3, 4, 8, and 9.

The controller 1110 may control signal flow between respective blocks toperform the methods described with respect to FIGS. 3, 4, 8, and 9. Thecontroller 1110 and the transceiver 1120 may not be implemented byseparate modules, or they may be implemented by one constituent unit inthe form of a single chip, a system on chip, etc. The controller 1110and the transceiver 1120 may be electrically connected to each other.For example, the controller 1110 may be a circuit, anapplication-specific circuit, or at least one processor. The basestation may be implemented by providing a memory device storingcorresponding program codes therein on a certain constituent unit in thebase station. The base station 1100 may also include any one of theaforementioned modules.

FIG. 12 is a diagram of a network entity, according to an embodiment.

A network entity 1200 may include a transceiver 1220 and a controller1210 configured to control the overall operation of the network entity1200. The transceiver 1220 may include a transmitter 1223 and a receiver1225. The network entity 1200 may further include a storage in additionto the transceiver 1220 and the controller 1210.

The transceiver 1220 may transmit/receive signals with other networkentities.

The controller 1210 may control the network entity 1200 to perform anyone of the methods described with respect to FIGS. 3, 4, 8, and 9.

The controller 1210 may control signal flow between respective blocks toperform the methods described with respect to FIGS. 3, 4, 8, and 9. Thecontroller 1210 and the transceiver 1220 may not be implemented byseparate modules, or they may be implemented by one constituent unit inthe form of a single chip, a system on chip, etc. The controller 1210and the transceiver 1220 may be electrically connected to each other.For example, the controller 1210 may be a circuit, anapplication-specific circuit, or at least one processor. The networkentity 1200 may be implemented by providing a memory device storingcorresponding program codes therein on a certain constituent unit in thebase station.

In accordance with the disclosure, a packet computation load of aterminal (user equipment (UE)) can be reduced, and the use of the radioresources for the QoS support can be saved. Further, the QoS reflectingvarious QoS requirements and backhaul network situations can be securedin the 5G backhaul network.

While the disclosure has been shown and described with reference tocertain embodiments thereof, it will be understood by those skilled inthe art that various changes in form and details may be made thereinwithout departing from the scope of the disclosure. Therefore, the scopeof the disclosure should not be defined as being limited to theembodiments, but should be defined by the appended claims andequivalents thereof.

What is claimed is:
 1. A method performed by a base station in awireless communication system, the method comprising: receiving, from asession management function (SMF) entity, information on transport levelpacket marking for uplink data of a terminal, wherein the informationincludes a differentiated services code point (DSCP) value; receiving,from the terminal, the uplink data; performing the transport levelpacket marking in an internet protocol (IP) header for the uplink databased on the DSCP value received from the SMF entity; and transmitting,to a user plane function (UPF) entity, the uplink data with the IPheader.
 2. The method of claim 1, wherein the transport level packetmarking is performed on a per quality of service (QoS) flow basis. 3.The method of claim 1, wherein the uplink data is transmitted to the UPFentity over an N3 tunnel.
 4. A method performed by a user plane function(UPF) entity in a wireless communication system, the method comprising:receiving, from a session management function (SMF) entity, informationon transport level packet marking for downlink data for a terminalwherein the information includes a differentiated services code point(DSCP) value; performing the transport level packet marking in aninternet protocol (IP) header for the downlink data based on the DSCPvalue received from the SMF entity; and transmitting, to a base station,the downlink data with the IP header.
 5. The method of claim 4, whereinthe transport level packet marking is performed on a per quality ofservice (QoS) flow basis.
 6. The method of claim 4, wherein the downlinkdata is transmitted to the base station in a tunnel between the UPFentity and the base station.
 7. A base station in a wirelesscommunication system, the base station comprising: a transceiver; and acontroller coupled with the transceiver and configured to: receive, froma session management function (SMF) entity, information on transportlevel packet marking for uplink data of a terminal, wherein theinformation includes a differentiated services code point (DSCP) value,receive, from the terminal, the uplink data, perform the transport levelpacket marking in an internet protocol (IP) header for the uplink databased on the DSCP value received from the SMF entity, and transmit, to auser plane function (UPF) entity, the uplink data with the IP header. 8.The base station of claim 7, wherein the transport level packet markingis performed on a per quality of service (QoS) flow basis.
 9. The basestation of claim 7, wherein the uplink data is transmitted to the UPFentity over an N3 tunnel.
 10. A user plane function (UPF) entity in awireless communication system, the UPF entity comprising: a transceiver;and a controller coupled with the transceiver and configured to:receive, from a session management function (SMF) entity, information ontransport level packet marking for downlink data for a terminal, whereinthe information includes a differentiated services code point (DSCP)value, perform the transport level packet marking in an internetprotocol (IP) header for the downlink data based on the DSCP valuereceived from th SMF entity, and transmit, to a base station, thedownlink data with the IP Header.
 11. The UPF entity of claim 10,wherein the transport level packet marking is performed on a per qualityof service (QoS) flow basis.
 12. The UPF entity of claim 10, wherein thedownlink data is transmitted to the base station in a tunnel between theUPF entity and the base station.
 13. A method performed by a terminal ina wireless communication system, the method comprising: generatinguplink data of the terminal; and transmitting, to a base station, theuplink data, wherein information on transport level packet marking forthe uplink data is received by the base station from a sessionmanagement function (SMF) entity, wherein the transport level packetmarking is performed by the base station in an internet protocol (IP)header for the uplink data based on the DSCP value received from the SMFentity, and wherein the uplink data with the IP header is transmitted bythe base station to a user plane function (UPF) entity.
 14. The methodof claim 13, wherein the transport level packet marking is performed ona per quality of service (QoS) flow basis.
 15. The method of claim 13,wherein the uplink data is transmitted to the UPF entity over an N3tunnel.
 16. A terminal in a wireless communication system, the terminalcomprising: a transceiver; and a controller coupled with the transceiverand configured to: generate uplink data of the terminal, and transmit,to a base station, the uplink data, wherein information on transportlevel packet marking for the uplink data is received by the base stationfrom a session management function (SMF) entity, wherein the transportlevel packet marking is performed by the base station in an internetprotocol (IP) header for the uplink data based on the DSCP valuereceived from the SMF entity, and wherein the uplink data with the IPheader is transmitted by the base station to a user plane function (UPF)entity.
 17. The terminal of claim 16, wherein the transport level packetmarking is performed on a per quality of service (QoS) flow basis. 18.The terminal of claim 16, wherein the uplink data is transmitted to theUPF entity over an N3 tunnel.